Ordinal
|
Description
|
Data Type
|
Data Length
|
Required
|
Check
Constraints
|
Comments
|
1
|
Item ID
|
string
|
25
|
Y
|
|
|
2
|
Price Sheet Code
|
string
|
30
|
|
|
This
field is used to identify a unique price sheet. Customer locations are
associated to a default price sheet in the storefront so base pricing can be
determined. If this is left blank, then the overall Price Sheet for the store
is used or Price Matrices may explicitly set the Price Sheet to use.
Examples: USA, STOREnn, BRANCHnn
|
3
|
Base Price
|
money
|
|
Y
|
|
This
is the base price for this item and price list. The storefront starts with
this number then applies any markups or discounts defined. This is also
referred to as list price.
|
4
|
Price Basis Code
|
string
|
30
|
|
|
This
field is a secondary filter to Price Sheet to determine customer specific
pricing. Examples: LIST, MSRP, WHOLESALE, RETAIL, COST)
|
5
|
Start Date
|
date
|
|
|
Must be a proper date
|
Defines
when this price will be in effect. Can be left blank which means effective
now until a future date is reached that activates a new price entry.
|
6
|
Price Per Qty
|
integer
|
|
Y
|
|
If the base prices defined for one (1) item are too small, this column may be used as a factor greater than 1. For example if the unit price for 1 unit is .0012, you may specify a price per quantity of 100 and a base price of .12. This technique is to improve accuracy of the calculation and is supported by some ERP systems. Generally the price per quantity is 1.
|
7
|
Price Per UOM
|
string
|
10
|
Y
|
|
Typically the base prices are specified in the default sales UOM but if not, an alternate pricing unit of measure can be specified. This unit of measure is used in conjunction with the price per quantity field. For example, you may price an item by the box (BX) but sell the item per each (EA) unit.
|